At the risk of being really stupid, but, is this Github rep still being managed by anyone?

Unfortunately, this is not such a stupid question :( @Paddy0174 last activities were more than a month ago. I have also tried to write to him via the Home Assistant forum. So far, unfortunately, without feedback.
I really hope that he is well

Yeah, unfortunately I don't know either and hope he's well too.

I too have written to him on the home assistant forum. No reply. Last seen approx 25 Nov.
And i don't have his private email address either.
🥺
Hope nothing has happened...

It should be possible to continue to maintain the code base because paddy created an organization for this repo instead of managing it on his own. But I don't know who was added to the Minimalist-UI org.

But let's hope he's fine first of all. 🤞

Unfortunately, if he hasn't added anyone to the organization, that won't do much good either. :-( Unfortunately, at least there are no public members: https://github.com/orgs/UI-Lovelace-Minimalist/people

Would one solution to this be that one with good knowledge, and maybe someone that we know has contributed to the projected forks this repo and immediately creates such an org for the FORK?

@schumijo or you @CM000n

Hi
@TBens and @Paddy0174 are administrators of this repo. I am only a contributor. I also wait for a 'hello' from paddy...but nothing for many weeks 🤞
Let's wait for few more days before thinking to a fork. I have some knowledge about the code but don't have a lot of time and a lot of knowledge about GitHub 😁

No need for a fork. If @TBens realy is an administrator of this Organisation he can also give admin rights to someone from the contributors. But yeah, let's wait some more days.

H, like I wrote already in #34
@TBens, has now given me the right for the UI repo. Unfortunately, I don't have the rights for the page repo to revise the wiki yet.
I would still include this card in the next release and close this PR here. I'll then make a separate bug in the page repo so we can update the wiki once someone has permission.

It looks like there are currently merge conflicts due to the recent changes in the DEV Branch. Could you please have another look at it @saxel

Sure, I'll look into it :)

@saxel since this change removed the option for scenes in the vertical buttons, how should we use a button to call a scene? (e.g., activate night mode, movie mode, away mode, etc.)

I duplicated card_vertical_buttons to make a custom card, and added the following to tap_action service:

if( entity.entity_id.startsWith("scene.") )
          return "scene.turn_on";

But I really don't want to maintain a custom card just for that. Is there a better way to do this using the existing card?

The inteded wyay of using the cards is to use inputboolean or inputselect to choose/ativate the scene and then have an automation that triggers on the state change to start/end the scene. With inputboolean you can toggle a scene and with input select swtich between scenes.

With an automation you can also store the current state of the entities and restore that afterwards. I can add support for the scene in the vertical button as well, I can submit a pr later today if you want to use it as you have before. Let me know.

The inteded wyay of using the cards is to use inputboolean or inputselect to choose/ativate the scene and then have an automation that triggers on the state change to start/end the scene. With inputboolean you can toggle a scene and with input select swtich between scenes.

With an automation you can also store the current state of the entities and restore that afterwards. I can add support for the scene in the vertical button as well, I can submit a pr later today if you want to use it as you have before. Let me know.

Trying to understand here -- so I should create an input boolean helper, then have that input boolean activate an automation to turn on the scene? Right now I only have the scenes created, but it shouldn't be too much trouble to create the helper and the automation that is triggered by the helper.

Or should it be even easier than that?

Not sure we need a code change yet; this might just be a knowledge gap on my part.

Yes, thats the approach. The original vertical buttons only supported input_select to switch between scenes, we just added the input_boolean to make it toggle. I think I added support for switch and light to support other requests. so making it toggle a scene is not that hard.

This is one of my automations that also create a snapshot of the entities which is restored when i untoggle the scene.

- id: '1640815805682'
  alias: Scene - Kitchen work
  description: ''
  trigger:
  - platform: state
    entity_id: input_boolean.scene_kitchen_work
  condition: []
  action:
  - choose:
    - conditions:
      - condition: state
        entity_id: input_boolean.scene_kitchen_work
        state: 'on'
      sequence:
      - service: scene.create
        data:
          snapshot_entities: light.kitchen_2
          scene_id: snapshot_kitchen_work
      - scene: scene.lights_kitchen_work
    default:
    - scene: scene.snapshot_kitchen_work
  mode: single

Yes, thats the approach. The original vertical buttons only supported input_select to switch between scenes, we just added the input_boolean to make it toggle. I think I added support for switch and light to support other requests. so making it toggle a scene is not that hard.

This is one of my automations that also create a snapshot of the entities which is restored when i untoggle the scene.

- id: '1640815805682'
  alias: Scene - Kitchen work
  description: ''
  trigger:
  - platform: state
    entity_id: input_boolean.scene_kitchen_work
  condition: []
  action:
  - choose:
    - conditions:
      - condition: state
        entity_id: input_boolean.scene_kitchen_work
        state: 'on'
      sequence:
      - service: scene.create
        data:
          snapshot_entities: light.kitchen_2
          scene_id: snapshot_kitchen_work
      - scene: scene.lights_kitchen_work
    default:
    - scene: scene.snapshot_kitchen_work
  mode: single

How does it go back to your stored snapshot after you toggle that input_boolean off? Is that just built-in behavior or do you have to define that in another automation?

Also for what it's worth I think I'm going with the input_select behavior which seems to automatically cycle between the scenes based on button presses. For example, I can set up several lighting scenes and control them as follows:

### INPUT SELECT ###
input_select:
  lighting_scene_select:
    name: lighting_scene_select
    options:
      - "scene.all_lights_on"
      - "scene.movie_mode"
      - "scene.sleep"
      # and so on...
    icon: mdi:lightbulb-multiple-outline

### AUTOMATION ###
- id: '1643064813719'
  alias: Set Lighting Scene from Selection
  description: ''
  trigger:
  - platform: state
    entity_id: input_select.lighting_scene_select
  condition:
  - condition: template
    # check to confirm state is actually changing
    value_template: '{{ trigger.to_state != trigger.from_state }}'
  action:
  - service: scene.turn_on
    data_template:
      entity_id: '{{ states(''input_select.lighting_scene_select'') }}
  mode: single

### BUTTON CARD ###
- type: 'custom:button-card'
  template: card_vertical_button
  entity: input_select.lighting_scene_select
  name: Lights On
  icon: mdi:lightbulb-multiple
  variables:
    ulm_card_vertical_button_state: scene.all_lights_on
    ulm_card_vertical_button_color: yellow

automation?

The default behavious is run when the button is off and this does the restore and runs the stored scene with the saved states